Checklist: Exchange Information Requirements (EIR)
Use this checklist to ensure the EIR is comprehensive, compliant with ISO 19650, and ready for inclusion in the Tender Package.
1. Strategic Definition (Getting Started)
- Review Owner's Objectives: Ensure OIR (Organizational Information Requirements) are clearly understood.
- Define Smart Fields: Complete project-specific details (Project Name, Code, Location).
- Operational Focus: Ensure requirements focus on what is needed for operations, not just how to model it.
- Standard Alignment: Verify alignment with local standards (e.g., ISO 19650, TW-BIM).
Why this matters: Completing the EIR ensures the Owner’s information needs are clearly defined before structuring how that information will be delivered. This creates a strong foundation for verification.
2. Technical Scope Definition
- Define Discipline Folders: Create clear breakdown for Architecture, Structure, MEP, etc.
- Element Granularity: Define specific tasks/elements (e.g., "Walls," "Air Terminals," "Chillers").
- Milestone Definition: Rename milestones to match project stages (e.g., "Tender," "Construction," "Handover/Operation").
- Asset Data Import: Import Client Asset Information Requirements (AIR) (e.g., via CSV or database link).
- Information Assignment: Assign specific data requirements (LOIN) to the "Operation" milestone for each asset.
Why this matters: Structuring requirements in a detailed scope makes responsibilities clear and ensures that Asset Information can be automatically verified against the model deliverables.
3. Contractual Integration (Tender Package)
- Document Compilation: Ensure the EIR document reflects the Owner’s strategic goals.
- Scope Verification: Confirm all discipline folders, tasks, and milestone assignments are correct.
- Final Export: Export the completed EIR—including the defined scope—as a single PDF/Contract Document.
Why this matters: Exporting a completed EIR turns defined requirements into a contract-ready deliverable. This enables the document to be used as part of a tender package, setting clear expectations for prospective teams.
Exchange Information Requirements (EIR) Checklist
1. Getting Started
- Review the pre-filled EIR sections and understand the Owner’s information needs
- Complete all highlighted Smart Fields in this EIR template
- Ensure your responses focus on operational needs, not delivery methods
- Follow any inline guidance provided within each section
Why this matters:
Completing the EIR ensures the Owner’s information needs are clearly defined before structuring how that information will be delivered. This creates a strong foundation for consistent scope definition, tendering, and verification.
2. Creating the EIR (in Scope)
Follow the instructions in the “Define the information requirements in Scope” section of this template to complete this step.
- Create discipline folders in Scope: Architecture, Mechanical, Electrical
- Add tasks under each folder: Interior Walls, Air Terminals, Mechanical Equipment, Lighting Fixtures, Cable Tray with Fittings
- Rename Milestone 1 to Operation
- Import the CSV: Plannerly Assignment Information Requirement Import Template.csv
- Assign the correct information requirements in the Operation column for each task (use the reference image provided)
Why this matters:
Structuring information requirements in Scope makes responsibilities clear and ensures requirements can be issued as part of a tender package. It connects the Owner’s needs to specific deliverables and disciplines in a way that can be verified and managed.
3. EIR as a Contract (Tender Package)
- Your EIR document is created in Docs and reflects the Owner’s strategic goal.
- Your Scope includes discipline folders, tasks, and Operation milestone assignments.
- Exported your completed EIR - including the defined scope - as a single document in the File Manager.
Why this matters:
Exporting a completed EIR turns defined requirements into a contract-ready deliverable. This enables the document to be used as part of a tender package, setting clear expectations for prospective teams.